Usage Note 40932: "Error: Cannot set AUTOCOMMIT=NO due to driver limitations" when using PROC IMPORT or PROC EXPORT
Errors might occur when you use the IMPORT and EXPORT procedures following a LIBNAME using the PCFILES engine. A sample log is shown below:
libname test pcfiles path='c:\sastest\mycars1.accdb';
NOTE: Libref TEST was successfully assigned as follows:
Engine: PCFILES
Physical Name: c:\sastest\mycars1.accdb
proc export data=sashelp.class
outfile='c:\sastest\myfilenew2.xlsx'
dbms=excelcs replace;
run;
ERROR: Cannot set AUTOCOMMIT=NO due to driver limitations.
ERROR: Error in the LIBNAME statement.
Connection Failed. See log for details.
NOTE: The SAS System stopped processing this step because of errors.
NOTE: PROCEDURE EXPORT used (Total process time):
real time 0.09 seconds
cpu time 0.03 seconds
To circumvent the problem, issue a LIBNAME libref CLEAR; statement to clear the LIBNAME statement before using the IMPORT or EXPORT procedures. For the example above, this would be as follows:
LIBNAME TEST CLEAR;
Operating System and Release Information
SAS System | SAS/ACCESS Interface to PC Files | Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft® Windows® for x64 | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft Windows Server 2003 for x64 | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft Windows Server 2008 for x64 | 9.2 TS2M3 | 9.3 TS1M0 |
64-bit Enabled AIX | 9.2 TS2M3 | 9.3 TS1M0 |
64-bit Enabled HP-UX | 9.2 TS2M3 | 9.3 TS1M0 |
64-bit Enabled Solaris | 9.2 TS2M3 | 9.3 TS1M0 |
HP-UX IPF | 9.2 TS2M3 | 9.3 TS1M0 |
Linux | 9.2 TS2M3 | 9.3 TS1M0 |
Linux for x64 | 9.2 TS2M3 | 9.3 TS1M0 |
Solaris for x64 | 9.2 TS2M3 | 9.3 TS1M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
When using IMPORT and EXPORT with the EXCELCS engine, errors might occur. These occur if a LIBNAME using the PCFILES engine has been used previously in the code and has not been cleared.
Date Modified: | 2010-12-21 12:48:41 |
Date Created: | 2010-09-17 09:49:49 |